Enhanced mechanisms for managing multidimensional data

ABSTRACT

An enhanced multidimensional data management system significantly reduces the resources required to convert a spreadsheet into an enterprise collaborative system. A spreadsheet may be imported as is without modifications. Additional information that cannot be automatically inferred about the data model used in the spreadsheet is obtained. Dimensions, timescale, and measure data are clearly defined and located. The spreadsheet is kept in the system in the form of both a spreadsheet and as a multidimensional data structure such as an online analytical processing (OLAP) cube or structure. This duality allows the spreadsheet to be manipulated as if it was an OLAP cube, modifying iterations within the dimensions, and the OLAP cube to be computed as if it was a spreadsheet.

TECHNICAL FIELD

The present disclosure relates to generating, managing, maintaining, and manipulating multidimensional data.

DESCRIPTION OF RELATED ART

Numerous entities maintain and manipulate multidimensional data by using spreadsheets. Spreadsheets have been widely adopted because they can be easily implemented by people who do not have an information technology (IT) background, reducing the need to have people with both business logic familiarity and technology expertise. However, large scale organizational and corporate systems relying on spreadsheets have a number of drawbacks.

For example, spreadsheet based systems lack of collaborative capabilities, suffer from version management deficiencies, do not scale well, and are prone to bugs. That is, adding significant amounts of data or a large number of users can stress a spreadsheet based system. Multiple different subgroups within an organization cannot easily synchronize versions and changes. Furthermore, spreadsheet systems are prone to errors since the business logic is not separated from the data imposing the logic to be repeated independently on every cell composing the spreadsheet. Auditability is poor as it takes a considerable amount of time to understand the business logic involved in a spreadsheet. Versioning is not natively supported inside the spreadsheet. For example, a spreadsheet does not track when the content of a cell is modified, i.e. only the new value is kept and the old value is lost.

Nevertheless, because of the simplicity in their implementation, spreadsheets very often correspond to a first attempt of addressing a business problem in an automated fashion. They are logically seen as a very precious source of information for IT people when implementing a more robust IT system as soon as the inconveniences of using spreadsheets are too restrictive. When building an IT solution, a lot of effort can be dedicated to analyzing the information in spreadsheets and to replicating the exact same results obtained by them. This process usually results in the discovery of many bugs and the slow convergence between the two systems.

Consequently, it is desirable to provide enhanced mechanisms for managing multidimensional data including mechanisms for analyzing, generating, manipulating, and maintaining multidimensional data in spreadsheet form and as multidimensional data structures that overcome some of the drawbacks of conventional systems.

Overview

An enhanced multidimensional data management system significantly reduces the resources required to convert a spreadsheet into an enterprise collaborative system. A spreadsheet may be imported as is without modifications. Additional information that cannot be automatically inferred about the data model used in the spreadsheet is input. Dimensions, timescale, and measure data are clearly defined and located. The spreadsheet is kept in the system in the form of both a spreadsheet and as a multidimensional data structure such as an online analytical processing (OLAP) cube or structure. A mapping produces a bi-directional link between the spreadsheet and the dimensions and iterations of an OLAP cube. This duality allows the spreadsheet to be manipulated as if it was an OLAP cube, modifying iterations within the dimensions, and the OLAP cube to be computed as if it was a spreadsheet.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may best be understood by reference to the following description taken in conjunction with the accompanying drawings, which illustrate particular embodiments of the present invention.

FIG. 1 illustrates one example of a spreadsheet and OLAP cube duality.

FIG. 2 illustrates one example of a flow process diagram.

FIG. 3 illustrates one example of entry of dimension information during importation of a spreadsheet.

FIG. 4 illustrates one example of entry of timescale information during importation of a spreadsheet.

FIG. 5 illustrates one example of entry of measures during importation of a spreadsheet.

FIG. 6 illustrates one example of a computer system.

DETAILED DESCRIPTION

Reference will now be made in detail to some specific examples of the invention including the best modes contemplated by the inventors for carrying out the invention. Examples of these specific embodiments are illustrated in the accompanying drawings. While the invention is described in conjunction with these specific embodiments, it will be understood that it is not intended to limit the invention to the described embodiments. On the contrary, it is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims.

For example, the techniques of the present invention will be described in the context of particular data structures such as online analytical processing (OLAP) cubes. However, it should be noted that the techniques of the present invention apply to a wide variety of different data structures and different types of multidimensional data. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. Particular example embodiments of the present invention may be implemented without some or all of these specific details. In other instances, well known process operations have not been described in detail in order not to unnecessarily obscure the present invention.

Various techniques and mechanisms of the present invention will sometimes be described in singular form for clarity. However, it should be noted that some embodiments include multiple iterations of a technique or multiple instantiations of a mechanism unless noted otherwise. For example, a system uses a processor in a variety of contexts. However, it will be appreciated that a system can use multiple processors while remaining within the scope of the present invention unless otherwise noted. Furthermore, the techniques and mechanisms of the present invention will sometimes describe a connection between two entities. It should be noted that a connection between two entities does not necessarily mean a direct, unimpeded connection, as a variety of other entities may reside between the two entities. For example, a processor may be connected to memory, but it will be appreciated that a variety of bridges and controllers may reside between the processor and memory. Consequently, a connection does not necessarily mean a direct, unimpeded connection unless otherwise noted.

Various organizations and enterprises rely on spreadsheets to organize, manipulate, and manage business data and logic. Spreadsheets are accessible to people without technology backgrounds because of their ease of use and relatively friendly user experiences. Spreadsheets have been widely adopted because they can be easily implemented by people who do not have an information technology (IT) background, reducing the need to have people with both business logic familiarity and technology expertise. Spreadsheets from certain vendors also have fairly robust ecosystems with add-ons and tools designed for use with those spreadsheets. However, conventional spreadsheets have a number of limitations. For example, spreadsheet based business systems lack collaborative capabilities. It is typically burdensome and error prone for different departments and different people to work on the same spreadsheet simultaneously. Individual spreadsheet files may be locked and unlocked for particular users, but this limits manipulation of the spreadsheet to a single user. If multiple versions of the same spreadsheet file are manipulated simultaneously, there is no easy way to synchronize the cells of the different spreadsheet files, even if there are technically no cell conflicts. Although spreadsheets can sometimes be shared, spreadsheet cells have no versioning mechanism, even if some outside tools may support versioning. For example, most third-party versioning and revision control tools can generate graphs of revisions and commits to allow tracking and comparison of modifications. However, they are difficult to use without technical skills. Although it may be difficult for many people from different departments to work independently on the same business data or logic maintained in spreadsheet files, it is even more difficult for many people to work together on the same cells, data, and logic within a spreadsheet simultaneously.

Collaborative limitations become even more apparent as an enterprise system is scaled. Many conventional spreadsheet based systems are not designed to scale and extensive efforts are required to allow them to grow as a business grows. Many spreadsheet based systems are designed to allow only one person to use the spreadsheet at a time. Data errors, business logic errors, and copy and paste errors become increasingly common because spreadsheets lack scaling, tracking, and validation mechanisms necessary for large systems. Auditability is poor as it takes a considerable amount of time to understand the business logic involved in a spreadsheet. Versioning is not natively supported inside the spreadsheet. For example, a spreadsheet does not track when the content of cell is modified and when the old value is forgotten. What-if analyses, where the business logic is applied to many datasets and the results compared to one another, may be possible only if they are originally included in the design of the spreadsheet.

Consequently, various embodiments of the present invention provide enhancements that allow more efficient and effective management of multi-dimensional data. According to various embodiments, an enhanced multidimensional data management system significantly reduces the resources required to convert a spreadsheet into an enterprise collaborative system. A spreadsheet may be imported as is without modifications. Additional information that cannot be automatically inferred about the data model used in the spreadsheet is collected from the user. Dimensions, timescale, and measure data along with other types of data as well as outputs can be clearly defined and located. The spreadsheet is kept in the system in the form of both a spreadsheet and as a multidimensional data structure such as an online analytical processing (OLAP) cube. A bidirectional mapping between the spreadsheet and the multidimensional data structure is maintained. This duality and bidirectional mapping allows the spreadsheet to be manipulated as if it was an OLAP cube, modifying iterations within the dimensions, and the OLAP cube to be computed as if it was a spreadsheet.

An existing spreadsheet can be kept as is. An enhanced multidimensional data management system is able to handle a variety of spreadsheets that were not initially designed with the objective of potential enhancements and modifications. Once the spreadsheet is imported into an enhanced multidimensional data management system, typical limitations due to the usage of spreadsheets vanish. The ability to collaborate between a large number of people is enhanced.

According to various embodiments, FIG. 1 shows one example of a spreadsheet and OLAP cube duality. Spreadsheet 101 may be part of a conventional business system maintaining both business data and business logic. An organization may wish to expand and enhance business system functionality. Some multidimensional management systems require importation and conversion of spreadsheet business data and business logic into their own proprietary formats. Conversion can often be problematic as data and logic may be lost or converted incorrectly. Formula translations from a conventional spreadsheet to an enhanced data management system may be error prone or imprecise. Nonetheless, some entities will exert Herculean efforts to convert conventional spreadsheet based solutions to proprietary enhanced spreadsheet or enhanced data management systems. However, even if the conversion process goes smoothly, the entity is still left with a proprietary system that may not have the support of 3^(rd) party vendors, may not be associated with a robust ecosystem, and may not be compatible with other existing entity resources.

It may be possible to convert proprietary system data back into a conventional spreadsheet format, but the conversion is again potentially error prone or imprecise. Furthermore, the reimport of these exported spreadsheets can also be problematic. Consequently, various embodiments of the present invention provide mechanisms for maintaining a conventional spreadsheet along with providing enhanced multi-dimensional data management functionality. According to various embodiments, conventional spreadsheet 101 may be maintained as both a spreadsheet 111 and an OLAP cube 113 in an enhanced multi-dimensional data management system (EMDMS) 121. Spreadsheet 111 in an enhanced multi-dimensional data management system 121 is also referred to herein as a server side generated spreadsheet or an enhanced multi-dimensional data management system generated spreadsheet. In particular example embodiments, the OLAP cube 113 includes dimensions 115, time scale 117 and measures information 119. According to various embodiments, changes made to the enhanced multi-dimensional data management system 121 are made both to the OLAP cube 113 and to the spreadsheet 111. In particular example embodiments, the enhanced multi-dimensional data management system 121 is associated with a server side spreadsheet engine compatible with standard format OpenXML. There is a bidirectional mapping between the spreadsheet engine and the OLAP structure or OLAP cube 113.

FIG. 2 illustrates one example of a flow process diagram for using an enhanced multi-dimensional data management system. In particular example embodiments, a conventional spreadsheet is selected for import into an enhanced multi-dimensional data management system at 201. According to various embodiments, at 203, the structure in the spreadsheet is identified based on cell formula and cell location as well as information provided by users and/or information already stored in a target system, e.g. referential data. Patterns can be identified based on cell relationships and OLAP mapping at 205. The user can then correct the model by redefining the identified structure between 203 and 205. According to various embodiments, calculations are performed using an embedded spreadsheet calculus engine and no formula translations are necessary at 207.

According to various embodiments, insertion and/or deletion of lines and rows can be based on the formula pattern and the layout to allow for automatic update of both an OLAP cube and the spreadsheet with enhanced functionality at 209. Similarly, values of cells can be modified and changes can be propagated accordingly to the OLAP cube. All scenarios are versioned at 211.

In particular example embodiments, export and reimport of a conventional spreadsheet is also allowed. Reimport of the conventional spreadsheet can trigger an update of the spreadsheet computed by the enhanced multi-dimensional data management system at 213.

After re-importing the data in the spreadsheet, the OLAP can be modified and then go back in the workflow at 207 as shown by the feedback arrow from 213 to 207.

FIG. 3 illustrates one example of entry of dimension information during importation of a spreadsheet. According to various embodiments, a spreadsheet 301 computed by an enhanced multi-dimensional data management system includes dimensions 311, measures 313, and timescales 315 corresponding to elements of an OLAP cube. During importation of a spreadsheet, a user might select particular entries as dimensions. For example, country 321 and product 323 may correspond to dimensions. Spreadsheet 301 computed by the enhanced multi-dimensional data management system may also include timescale information. Examples of measures information may include sales 331, cost of sales 333, gross profit 335, and gross margin 337.

As shown in the present embodiment, the dimensions of the EMDMS spreadsheet 301 are being set, as indicated by the checked box in the tools area. A check box allows a user to switch between two different modes. In the outline dimensions mode, cells that belong to a dimension/time axis/set of measures are colored. Different dimensions/time axis/set of measures are colored differently. A user does not necessarily have to be in this mode to select dimensions/time axis/set of measures. However, it is useful since a user has an immediate overview of the cells that already are part of a dimension/time axis/set of measures. In particular, the “Outline Dimensions” box is checked, indicating that the EMDMS spreadsheet 301 is in this mode. In the present example, country 321 is already selected and listed as one of the dimensions 311, as indicated in the area listed below the tools section. A product P1, located in cell B13, is being added as a new dimension 311 from the pulldown menu shown. Once selected, this product 323 will be added to the dimensions 311 area below the tools section and above the cells.

FIG. 4 illustrates one example of entry of timescale information during importation of a spreadsheet. According to various embodiments, a spreadsheet 401 computed by an enhanced multi-dimensional data management system includes dimensions 411, measures 413, and timescales 415 corresponding to elements of an OLAP cube. During importation of a spreadsheet, a user might select particular timescales corresponding to particular time periods such as months, quarters, and years. Spreadsheet 401 may also include dimensions 411 such as country 421 and product 423. Other examples may include SKU, indications, dosage, etc. Examples of measures information may include sales 431, cost of sales 433, gross profit 435, and gross margin 437.

As shown in the present embodiment, the dimensions of the EMDMS spreadsheet 401 are being set, as indicated by the checked box in the tools area. A check box allows a user to switch between two different modes. In the outline dimensions mode, cells that belong to a dimension/time axis/set of measures are colored. Different dimensions/time axis/set of measures are colored differently. A user does not necessarily have to be in this mode to select dimensions/time axis/set of measures. However, it is useful since a user has an immediate overview of the cells that already are part of a dimension/time axis/set of measures. In particular, the “Outline Dimensions” box is checked, indicating that the EMDMS spreadsheet 401 is in this mode. In the present example, country 421 and product 423 are already selected and listed as two of the dimensions 411, as indicated in the area listed below the tools section. Timescales 415 are now being selected. In particular, the year 2017, located in cell E1, is being added as a new timescale 415 from the pulldown menu shown. Once selected, this year will be added to the timescales 415 area below the tools section and above the cells.

FIG. 5 illustrates one example of entry of measures information during importation of a spreadsheet. According to various embodiments, a spreadsheet 501 computed by an enhanced multi-dimensional data management system includes dimensions 511, measures 513, and timescales 515 corresponding to elements of an OLAP cube. During importation of a spreadsheet, a user might select particular measures corresponding to elements such as sales 531, cost of sales 533, gross profit 535, and gross margin 537. A user may also enter timescales 515 corresponding to particular time periods such as months, quarters, and years. Spreadsheet 501 may also include dimensions 511 corresponding to country 521 and product 523.

As shown in the present embodiment, the dimensions of the EMDMS spreadsheet 501 are being set, as indicated by the checked box in the tools area. A check box allows a user to switch between two different modes. In the outline dimensions mode, cells that belong to a dimension/time axis/set of measures are colored. Different dimensions/time axis/set of measures are colored differently. A user does not necessarily have to be in this mode to select dimensions/time axis/set of measures. However, it is useful since a user has an immediate overview of the cells that already are part of a dimension/time axis/set of measures. In particular, the “Outline Dimensions” box is checked, indicating that the EMDMS spreadsheet 501 is in this mode. In the present example, country 521 and product 523 are already selected and listed as two of the dimensions 511, as indicated in the area listed below the tools section. In addition, year 541 has already been selected as a timescale 515, as indicated in the timescales area 515 below the tools area and above the cells. On this screen, measures 513 have just been selected. In particular, gross profit 535, located in cell C15, has been added as a new measure 513, along with sales 531, cost of sales 533, and gross margin 537, as listed in the measures 513 area below the tools section and above the cells.

According to various embodiments, the EMDMS spreadsheet includes improved functionality over the originally imported spreadsheet. In particular, by specifying parameters such as dimensions, measures, and timescales, data is accurately mapped and can be tracked more effectively. Additionally, errors in calculations or data entry can be more easily detected. Moreover, formulas applied to particular cells can be accurately outlined using these parameters.

According to various embodiments, insertion of data into an OLAP cube will insert or remove rows and columns corresponding to the data in the EMDMS spreadsheet with appropriate formulas and styles. Existing formulas will also be modified. For example, insertion of data into the OLAP cube will change summations and totals included in the EMDMS spreadsheet.

Various computing devices can implement the methods described. For instance, a mobile device, computer system, etc. can be used to generate artificially rendered images. With reference to FIG. 6, shown is a particular example of a computer system that can be used to implement particular examples of the present invention. For instance, the computer system 600 can be used to provide generate artificially rendered images according to various embodiments described above. In addition, the computer system 600 shown can represent a computing system on a mobile device. According to particular example embodiments, a system 600 suitable for implementing particular embodiments of the present invention includes a processor 601, a memory 603, an interface 611, and a bus 615 (e.g., a PCI bus). The interface 611 may include separate input interface 613 and output interface 615, or may be a unified interface supporting both operations. When acting under the control of appropriate software or firmware, the processor 601 is responsible for such tasks such as optimization. Various specially configured devices can also be used in place of a processor 601 or in addition to processor 601. The complete implementation can also be done in custom hardware. The interface 611 is typically configured to send and receive data packets or data segments over a network. Particular examples of interfaces the device supports include Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like.

In addition, various very high-speed interfaces may be provided such as fast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control and management.

According to particular example embodiments, the system 600 uses memory 603 to store data and program instructions and maintain a local side cache. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to store received metadata and batch requested metadata.

Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to tangible, machine readable media that include program instructions, state information, etc. for performing various operations described herein. Examples of machine-readable media include hard disks, floppy disks, magnetic tape, optical media such as CD-ROM disks and DVDs; magneto-optical media such as optical disks, and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and programmable read-only memory devices (PROMs). Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.

Although many of the components and processes are described above in the singular for convenience, it will be appreciated by one of skill in the art that multiple components and repeated processes can also be used to practice the techniques of the present disclosure.

While the present disclosure has been particularly shown and described with reference to specific embodiments thereof, it will be understood by those skilled in the art that changes in the form and details of the disclosed embodiments may be made without departing from the spirit or scope of the invention. It is therefore intended that the invention be interpreted to include all variations and equivalents that fall within the true spirit and scope of the present invention. 

1. A method comprising: identifying a structure in a conventional spreadsheet based on cell formula and cell location during import of the conventional spreadsheet, the structure in the conventional spreadsheet including a set of cells; bi-directionally mapping the set of cells to iterations and aggregations on a multidimensional data structure, wherein the mapping associates ranges and objects from the multidimensional data structure, wherein the multidimensional data structure is an online analytical processing (OLAP) structure; identifying patterns based on cell relationships and OLAP mapping; maintaining a duality and bi-directional mapping between the conventional spreadsheet and the OLAP structure and avoiding formula translations, wherein maintaining the duality and bi-directional mapping includes performing calculations using an embedded spreadsheet calculus engine such that no formula translations are necessary, wherein the duality and bidirectional mapping allows the spreadsheet to be manipulated as if it was an OLAP cube, modifying iterations within the dimensions, and the OLAP cube to be computed as if it was a spreadsheet; generating an enhanced collaborative spreadsheet using the OLAP structure; receiving modifications to the enhanced collaborative spreadsheet and the corresponding OLAP structure, wherein modifications to the conventional spreadsheet are made to match the data modified in the OLAP structure, wherein modifications include inserting or deleting lines and rows to allow for automatic update of the OLAP structure and the enhanced collaborative spreadsheet; and versioning all scenarios of modifications, wherein each cell in the set of cells includes a versioning mechanism, and wherein versioning is not natively supported inside the conventional spreadsheet.
 2. The method of claim 1, wherein modifying iterations to dimensions/measures/timescale in an OLAP structure modifies rows/columns in the enhanced collaborative spreadsheet along with corresponding formulas.
 3. The method of claim 1, wherein enterprise wide spreadsheets can be merged into an OLAP structure according to an existing spreadsheet.
 4. The method of claim 1, further comprising receiving modifications to the conventional spreadsheet, wherein modifications to the conventional spreadsheet are propagated as modifications to the OLAP structure.
 5. The method of claim 1, further comprising maintaining a bidirectional mapping between the enhanced collaborative spreadsheet and the OLAP structure.
 6. The method of claim 1, further comprising updating the OLAP structure during re-import of the conventional spreadsheet.
 7. The method of claim 1, wherein a plurality of conventional spreadsheets are modified at a plurality of client devices.
 8. The method of claim 1, wherein the OLAP structure is maintained at a server.
 9. The method of claim 1, wherein a server side spreadsheet engine is used to evaluate formulas.
 10. The method of claim 1, wherein the enhanced collaborative spreadsheet is compatible with OpenXML.
 11. The method of claim 1, wherein dimension, measure, and timescale information are received during import of the conventional spreadsheet.
 12. The method of claim 11, wherein dimension, measure, and timescale information are used to generate the OLAP structure.
 13. The method of claim 1, wherein the OLAP structure is an OLAP cube.
 14. A non-transitory computer readable medium comprising: computer code for identifying a structure in a conventional spreadsheet based on cell formula and cell location during import of the conventional spreadsheet, the structure in the conventional spreadsheet including a set of cells; computer code for mapping the set of cells to iterations and aggregations on a multidimensional data structure, wherein the multidimensional data structure is an online analytical processing (OLAP) structure; computer code for identifying patterns based on cell relationships and OLAP mapping; computer code for maintaining a duality and bi-directional mapping between the conventional spreadsheet and the OLAP structure and avoiding formula translations, wherein maintaining the duality and bi-directional mapping includes performing calculations using an embedded spreadsheet calculus engine such that no formula translations are necessary, wherein the duality and bidirectional mapping allows the spreadsheet to be manipulated as if it was an OLAP cube, modifying iterations within the dimensions, and the OLAP cube to be computed as if it was a spreadsheet; computer code for generating an enhanced collaborative spreadsheet using the OLAP structure; computer code for receiving modifications to the enhanced collaborative spreadsheet and the corresponding OLAP structure, wherein modifications to the conventional spreadsheet are made to match the data modified in the OLAP structure, wherein modifications include inserting or deleting lines and rows to allow for automatic update of the OLAP structure and the enhanced collaborative spreadsheet; and computer code for versioning all scenarios of modifications, wherein each cell in the set of cells includes a versioning mechanism, and wherein versioning is not natively supported inside the conventional spreadsheet.
 15. The non-transitory computer readable medium of claim 14, wherein modifying iterations to dimensions/measures/timescale in an OLAP structure modifies rows/columns in the enhanced collaborative spreadsheet along with corresponding formulas.
 16. The non-transitory computer readable medium of claim 14, wherein enterprise wide spreadsheets can be merged into an OLAP structure according to an existing spreadsheet.
 17. The non-transitory computer readable medium of claim 14, further comprising receiving modifications to the conventional spreadsheet, wherein modifications to the conventional spreadsheet are propagated as modifications to the OLAP structure.
 18. A system comprising: a processor; and memory, wherein the memory includes instructions for causing the processor to execute a method, the method comprising: identifying a structure in a conventional spreadsheet based on cell formula and cell location during import of the conventional spreadsheet, the structure in the conventional spreadsheet including a set of cells; mapping the set of cells to iterations and aggregations on a multidimensional data structure, wherein the multidimensional data structure is an online analytical processing (OLAP) structure; identifying patterns based on cell relationships and OLAP mapping; maintaining a duality and bi-directional mapping between the conventional spreadsheet and the OLAP structure and avoiding formula translations, wherein maintaining the duality and bi-directional mapping includes performing calculations using an embedded spreadsheet calculus engine such that no formula translations are necessary, wherein the duality and bidirectional mapping allows the spreadsheet to be manipulated as if it was an OLAP cube, modifying iterations within the dimensions, and the OLAP cube to be computed as if it was a spreadsheet; generating an enhanced collaborative spreadsheet using the OLAP structure; receiving modifications to the enhanced collaborative spreadsheet and the corresponding OLAP structure, wherein modifications to the conventional spreadsheet are made to match the data modified in the OLAP structure, wherein modifications include inserting or deleting lines and rows to allow for automatic update of the OLAP structure and the enhanced collaborative spreadsheet; and versioning all scenarios of modifications, wherein each cell in the set of cells includes a versioning mechanism, and wherein versioning is not natively supported inside the conventional spreadsheet.
 19. The system of claim 18, wherein modifying iterations to dimensions/measures/timescale in an OLAP structure modifies rows/columns in the enhanced collaborative spreadsheet along with corresponding formulas.
 20. The system of claim 18, wherein enterprise wide spreadsheets can be merged into an OLAP structure according to an existing spreadsheet 